My wife had been whining that she couldn't tell what time it was in the car, so I set the time format to "clock". I also put the developer image on the unit, so I could try to figure out how to bypass the "can't set the timezone" problem in 2.0b11. Never did find that out, but that's another story. I then went on a 10 hour trip. A few times I noticed my visual went away. Finally, I noticed why. The player app was restarting, but the unit was not rebooting.Attaching a serial cable showed it (the player application) was crashing. I reinstalled the consumer 2.0b11 image. Still crashing. I disabled the "clock" time format, and lo, no crash.

Fluke, or has anyone else seen this?

This is the first I've heard of this happening. Does anyone else run the clock display 100 percent of the time?

Also note: There is no "can't set the time zone" bug in beta 11. What it is, is a "time zone menu always defaults to US-Alaska even when my time zone is set correctly". This is known and will be fixed in the next release, and as far as I know, it's cosmetic-only. This is unrelated to the other issue you were describing.

This is the first I've heard of this happening. Does anyone else run the clock display 100 percent of the time?

Maybe. Just the other day I remarked to myself "Hey, the Empeg hasn't been spontaneously rebooting lately. What changed?" Well, aside from some Hijack updates, the main change is that I haven't been running clock visuals (I did for a while). I'll switch back to see if it starts rebooting. It also froze several times -- I'd leave it running overnight and find clock showing frozen time display from middle of the night.

Uh oh, the evidence mounts. Wonder if there's a bug in there someplace?

Anyone else?

Well, this isn't the clock visual, but yeah, I guess the code is probably the same.

And yeah, sorry for the poor phrasing of the "time zone selection" point, which yes, I realize is unrelated.

I'm not sure that this is what your asking for. I run the clock all the time. This is to say that I use the track info screen with the clock enabled. I rarely use the visuals. I have not had a problem with this Mk2a rebooting. The first Mk2a I purchased does reboot on occasion using the same format. it is a 30gb while the stable one is a 20bg.

My wife had been whining [...] Fluke, or has anyone else seen this?

Has anyone seen this with beta 13? I've just fixed a specific bug to do with failing to restart the player when synchronising with timemode set to clock, but haven't seen it crash during playback.

Peter

<DELETED> double post </DELETED>

i've figured out that this is what was happening to me in this thread.

here's the thing. if i leave it on clock time format, with Line INFO and visual Spectrolog128 (i haven't tried this w/ any other visual, but i will tonight), i get a player segfault in serial output but without the dump.

but if i use transient instead... i've been able to play all night without a crash.

this is in b13 version... i've seen it happen with or without hijack.

Now bug 1868 in the internal database.

overnight playing using funnelweb, line, and clock = crash.

interestingly, this time i had preinit loaded, and it showed that it went thru the M##scripts again (not the begining tho. didnt echo "empeg-preinit starting..." after the crash. the first line was the first M##script echoing "emptris v1.3 starting..."

nice. just happened to me again in AC mode. this time, a dump was echoed, but it didnt start from preinit. it just restarted the player. the only other post that included a code 0 and Unable to handle kernel paging request at virtual address 0000fff4 is here.



player(42): memory violation at pc=0x0207b538, lr=0x02073a94 (bad address=0x0436
8970, code 0)
pc : [<0207b538>] lr : [<02073a94>]
sp : bdfffc08 ip : bdfffc18 fp : bdfffc14
r10: 00000020 r9 : 00000000 r8 : 0214fa30
r7 : 0219cac0 r6 : 00000000 r5 : 02169810 r4 : bdfffc64
r3 : 021b44f0 r2 : 00000000 r1 : 021b4480 r0 : bdfffc64
Flags: nzCv IRQs on FIQs on Mode USER_32 Segment user
Control: C0D9D17D Table: C0D9D17D DAC: 00000015
Function entered at [<0207b520>] from [<02073a94>]
Function entered at [<02073a48>] from [<0201a678>]
r4 = 02118BC4
Function entered at [<0201a1d8>] from [<02067804>]
r10 = 0214F884 r9 = BDFFFD0C r8 = BDFFFD20 r7 = 0214FA30
r6 = 02168724 r5 = 00000001 r4 = 02168680
Function entered at [<02067774>] from [<020647c8>]
r7 = BDFFFD1C r6 = 0214F7A8 r5 = 0214FA30 r4 = 0214F7A8
Function entered at [<0206476c>] from [<02064f50>]
r5 = 0214F884 r4 = 0214F7A8
Function entered at [<02064f24>] from [<0206526c>]
r4 = 00000000
Function entered at [<02065030>] from [<02064f88>]
r10 = 020AAF94 r9 = 0214F7A8 r8 = 0000340E r7 = 00000080
r6 = 0000000E r5 = 0214F7A8 r4 = BDFFFD64
Function entered at [<02064f78>] from [<020ab04c>]
Function entered at [<020aaf94>] from [<020b18b0>]
r5 = 0214F7C0 r4 = BDFFFE40
Function entered at [<020b17e8>] from [<020e6c4c>]
r4 = 00000000
Function entered at [<020e53c0>] from [<020b162c>]
r8 = 0215306C r7 = 02153058 r6 = 020AAF94 r5 = 00000007
r4 = 00000000
Function entered at [<020b157c>] from [<020e6c4c>]
r5 = 00000000 r4 = 00000000
Function entered at [<021ad284>] from [<00000003>]
Unable to handle kernel paging request at virtual address 0000fff4
memmap = C0D9C000, pgd = c0d9c000
*pgd = c0f2f801, *pmd = c0f2f801, *pte = 00000000, *ppte = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c00f0c78>] lr : [<c00197d0>]
sp : c07adf44 ip : c07adf00 fp : c07adf90
r10: 00000000 r9 : c0f8b160 r8 : 0000000c
r7 : 00000000 r6 : 021ad284 r5 : 00010000 r4 : 00010000
r3 : 0000435b r2 : 001d25bb r1 : 021adc00 r0 : bffffbf8
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
Control: C0D9D17D Table: C0D9D17D DAC: 00000015
Process player (pid: 42, stackpage=c07ad000)
Stack:
c07adf20: c00197d0 c00f0c78 600000
13
c07adf40: ffffffff c0f8b178 c0f8aae0 c07ac000 c07adfb8 04368970 c0011a88 02073a
94
c07adf60: 04368970 00000000 c07adfb8 00000005 04368970 00000000 00000000 000000
00
c07adf80: 00000020 c07adfb4 c07adf94 c0011fc0 c0011838 c011297c 02169810 000000
00
c07adfa0: 0219cac0 0214fa30 00000000 c07adfb8 c000a0a8 c0011ee8 bdfffc64 021b44
80
c07adfc0: 00000000 021b44f0 bdfffc64 02169810 00000000 0219cac0 0214fa30 000000
00
c07adfe0: 00000020 bdfffc14 bdfffc18 bdfffc08 02073a94 0207b538 20000010 ffffff
ff
Backtrace:
Function entered at [<c001182c>] from [<c0011fc0>]
r10 = 00000020 r9 = 00000000 r8 = 00000000 r7 = 00000000
r6 = 04368970 r5 = 00000005 r4 = C07ADFB8
Function entered at [<c0011edc>] from [<c000a0a8>]
r8 = 0214FA30 r7 = 0219CAC0 r6 = 00000000 r5 = 02169810
r4 = C011297C
Code: e1140007 1afffff7 (e814000f) e1a05000 e0436008
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
Abnormal player termination
Player received signal 11
Starting player

Using non-standard cache size 102 (adjustment 32)
player.cpp : 385:empeg-car 2.00-beta13 2002/07/24.
Prolux 4 empeg car - 2.1434 Jul 24 2002
Vcb: 0x4066d000
! mp3_decoder.cpp :1049:Failed to find valid sync after seeking to offset 1485
400, error=0xc0044000

Some other thread has where I reported the output from the player; I do suspect it's the same, and I should look, for curiousity. This is an issue which still plagues me, and I'm tempted to try to work up something to be LD_PRELOADed for Std::String::Terminate which as I recall was the guilty party.

I have also noticed somthing like this, when I have the clock on, the display will flick off then on it is very fast maybe half a sec. but it only does this when I have the clock displayed. So far it has not crashed or rebooted but the display will flick maybe every 10 sec. or so. Oh also Im running b13 hijack 289 I know I know hijack is up to 300 now, Im just lazy.

Yup, this has been happening to me and my friend for a long time in b13. I use the scope visualization. Line info mode = crash, Transient = no problem. Twould be great if there were a fix since I like the Line info mode more than Transient most of the time.

-Ryan.

Line info mode = crash, Transient = no problem.

Can you verify whether the problem is with the "Clock" time format specifically? Or any timecode in Info:Line mode?

i've only seen it in clock mode. i'll leave it overnight at something else, and see what happens.

I ran it yesterday afternoon using both modes and never got a reboot. Since it's a random thing, it's going to be difficult to say for sure. I'll run the timecode in 'elapsed' mode for a while and report if I ever get a reboot.

-Hoagy.

Okay, great. Thanks.

Now bug 1868 in the internal database.

FITNR: the timemode=clock thing, and the clock visual thing, and possibly also the flick-to-black thing. Altogether quite a nasty one.

Peter

Just so you know, I'm having the same thing happen in 2b13 (consumer and developer). I have line info with clock and visuals. The unit crashes about every 2 hours. It did the same thing with my old one before it was stolen.

It still crashes even if the song is paused.

-Biscuits